The post-installation steps for SAS Real-Time Decision Manager that are documented in the Instructions.html file contain some minor errors that are detailed below.

1. In the section Create Federation Server Database Data Source Name, perform the following task after Step 2.
   To create the federation server database data source name, perform the following steps: 1. Click the DSNs tab. 2. Select New Data Source Name.
   Perform the following:
   For Select Data Service: Oracle_ds, substitute the name of the Data Service for your own environment.
   3. Enter Name: Oracle_dsn 4. Click OK.
2. In the section Integrate with Marketing Automation, change the path for Item 8 to include the release number.

   The current text reads as follows:

   Item 8: Select to import your–SASHOME\SASCustomerIntelligenceReportingMidTier\Config\Deployment\packages\cicactsr.spk.

   This is the correct text for Item 8:

   Select to import your–SASHOME\SASCustomerIntelligenceReportingMidTier\5.41\Config\Deployment\packages\cicactsr.spk.
3. In the section Create Authentication Server Users, creating fedadmin is included twice. You need to create fedadmin only once.
   
   
4. In the section SAS Customer Intelligence Reporting, repeat the instructions below for the corresponding resources under the /System/Applications/SAS Decision Services 5.5/SASDSEngineRepository folder.
   You must update the resources URL for these objects before using them. # Using the SAS Management Console, navigate to the /System/Applications/SAS # Decision Services/SAS Decision Services 5.5/SASDSDesignRepository folder. # Right Click on the CIConfirmTreatment resource and choose Edit System Resource . # Replace your-midtier-server with racsol03032.unx.sas.com. # Replace your-midtier-port with 9085. # Right Click on CIContactHistory resource and choose Edit System Resource . # Replace your-midtier-server with racsol03032.unx.sas.com. # Replace your-midtier-port with 9085. # Right Click on CIResponseHistory resource and choose Edit System Resource . # Replace your-midtier-server with racsol03032.unx.sas.com. # Replace your-midtier-port with 9085.
5. In the Instructions.html file for the Windows client tier, there are steps for changing the clientConfigServiceURL for SAS® Marketing Automation Launcher. These steps are not necessary because the URL is already configured properly.
   
   
6. There are steps for editing the DMStudio.config file that are detailed in the SAS® Decision Services configuration instructions. However, if SAS® Data Management Studio is included in your plan file, your original edits might be overwritten. If this problem occurs, SAS Data Management Studio is not able to connect to the DataFlux^® Federation Server. You might see the following error when you attempt to connect:
   Can't open the Authentication Service
   If this problem occurs, edit the DMStudio.config file again as detailed in the SAS Decision Services configuration instructions.

Operating System and Release Information